Hey 👋 @tannerlinsley

I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after:

![Skill Review Score Card](score_card.png)

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| router-core-ssr | 59% | 100% | +41% |
| router-core-auth-and-guards | 64% | 100% | +36% |
| router-core-navigation | 66% | 100% | +34% |
| start-core | 70% | 100% | +30% |
| react-start | 71% | 100% | +29% |
| router-core-code-splitting | 71% | 100% | +29% |
| router-core-not-found-and-errors | 71% | 100% | +29% |
| solid-start | 71% | 100% | +29% |
| start-core-execution-model | 71% | 100% | +29% |
| start-core-middleware | 71% | 100% | +29% |
| start-core-server-functions | 71% | 100% | +29% |
| start-core-server-routes | 71% | 100% | +29% |
| compositions-router-query | 75% | 100% | +25% |
| react-router | 75% | 100% | +25% |
| router-core-data-loading | 75% | 100% | +25% |
| router-core-search-params | 75% | 100% | +25% |
| solid-router | 75% | 100% | +25% |
| start-server-core | 75% | 100% | +25% |
| vue-router | 75% | 100% | +25% |
| vue-start | 75% | 100% | +25% |
| router-core-path-params | 71% | 96% | +25% |
| router-core-type-safety | 71% | 93% | +22% |
| start-core-deployment | 73% | 94% | +21% |
| virtual-file-routes | 80% | 96% | +16% |
| router-plugin | 84% | 100% | +16% |
| router-core | 84% | 94% | +10% |
| lifecycle-migrate-from-nextjs | 91% | 100% | +9% |
| lifecycle-migrate-from-react-router | 88% | 89% | +1% |

<details>
<summary>Changes made</summary>

**Frontmatter description improvements (all 28 skills):**
- Converted descriptions from YAML block scalar (`>-`) to quoted strings for consistency
- Added "Use when..." clauses with natural trigger terms so agents can better match skills to user intent
- Transformed API-dump style descriptions into action-oriented summaries that describe what the skill helps accomplish
- Explicitly mentioned "TanStack Router" or "TanStack Start" in each description for distinctiveness
- Preserved all key API names within the improved descriptions

**Name field fixes (17 sub-skills):**
- Fixed skill names containing `/` (e.g. `router-core/ssr` → `router-core-ssr`) which caused validation failures and 0% scores. Names now use kebab-case as required by the spec.

**Description field fixes (2 skills):**
- Removed generic type notation (`Accessor<T>`, `Ref<T>`) from solid-router and vue-router descriptions that was triggering XML tag validation errors.

**No body content was modified** — the existing skill content scored 85-100% on content dimensions. All changes are limited to frontmatter metadata.

</details>

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@yogesh-tessl](https://github.com/yogesh-tessl) - if you hit any snags.

Thanks in advance 🙏